-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create overview page for the suspicious replica recoverer daemon #373
Create overview page for the suspicious replica recoverer daemon #373
Conversation
The text is OK. I would add a schema describing the state machine similar to https://github.com/rucio/documentation/blob/main/website/static/img/request_state_transition_chart.svg even if it might be a bit complicated to fit everything in just one figure |
Can you add a reference to this page here? Could be useful to also understand why replicas become suspicious in the first place and where the recoverer daemon comes in |
Ping @ChristophAmes would you mind still doing these changes? |
I spent a while to read this daemon's code and adapt it into CMS. I'd like to add things into its documentation including this flow chart [1] and how it should be configured [2], which isn't trivial. If this PR is going to merged, I can wait and make a new PR to add my changes. [1]https://cmsdmops.docs.cern.ch/CMSRucio/Daemon_configurations/image.png |
326d12c
to
1f1a888
Compare
Sorry I haven't responded, I've been rather busy. |
1f1a888
to
fa7ed96
Compare
Now that this PR is closed, would you mind adding in the diagrams you linked? |
Sure, here it is: #452 |
The suspicious replica recoverer daemon isn't easy to understand at first glance. Therefore, an overview page for the suspicious replica recoverer daemon will be created, which will explain the general structure of the daemon and what the goals of each step are.